I am looking for a way to control which baseline of a module a user is able to view when opening a module. Essentially I want to be able to prevent people from getting the 'current' view of the module unless they are a member of a particular group. Is there an 'easy' way to acheive this ? NickGP - Tue Jun 18 04:28:50 EDT 2013 |
Re: Baseline Access Control Interesting question but I really don't believe this is possible. You can only access a baseline (from the GUI) by opening the current version of the module. There is also no way to have different access rights on baselines (they're read-only anyway) than on the current module - they're read-only so you cannot change them to set different permissions and when you take the baseline it makes a copy of the current module version, so any read access permissions will be inherited (if you can read current you can read baselined versions). |
Re: Baseline Access Control BillTidy - Tue Jun 18 10:19:51 EDT 2013 Interesting question but I really don't believe this is possible. You can only access a baseline (from the GUI) by opening the current version of the module. There is also no way to have different access rights on baselines (they're read-only anyway) than on the current module - they're read-only so you cannot change them to set different permissions and when you take the baseline it makes a copy of the current module version, so any read access permissions will be inherited (if you can read current you can read baselined versions). I suspected it was a long shot, but thought I would pose the question just in case someone had already done this. I had though about using dxl to specify a trigger so that when modules are opened, a prompt (gui) is displayed to ask the user to specify the baseline they want to view. |